0.3.66: adopt ciris-server 0.5.203 — a split node signs its consent as itself - #78
Merged
Merged
Conversation
…s itself The pin moves v0.5.202 -> v0.5.203; the substrate is unchanged, so the lock moves exactly the server and lens-core entries. 0.5.203 fixes CIRISServer#563 (agent-hosted split-key nodes: the consent guard, the held node pen, the served key record). This node is standalone — its configured key IS the node — so none of that path runs here; the pin moves so the two nodes on the canonical host run one server build. clippy -D warnings clean, 114 tests pass, `cargo metadata --locked` proves the lock (version bumped before the refresh), one copy of each crate. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Contributor
Author
|
CI note, not a pin problem: That is the mallinfo2 flake the server hit on the same test in its own |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The pin moves v0.5.202 -> v0.5.203; the substrate is unchanged, so the lock
moves exactly the server and lens-core entries. 0.5.203 fixes CIRISServer#563
(agent-hosted split-key nodes: the consent guard, the held node pen, the
served key record). This node is standalone — its configured key IS the
node — so none of that path runs here; the pin moves so the two nodes on the
canonical host run one server build.
clippy -D warnings clean, 114 tests pass,
cargo metadata --lockedprovesthe lock (version bumped before the refresh), one copy of each crate.
🤖 Generated with Claude Code